[SPARK-47700][SQL] Fix formatting of error messages with treeNode#45825
Closed
jchen5 wants to merge 2 commits into
Closed
[SPARK-47700][SQL] Fix formatting of error messages with treeNode#45825jchen5 wants to merge 2 commits into
jchen5 wants to merge 2 commits into
Conversation
Contributor
Author
|
Updated, CI is passing now |
Member
|
Merged to master. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Fix formatting of error messages.
Example: In several error messages, we are concatenating the plan without any separation:
in this locationFilter (dept_id#652. We should add a colon and space or newline in between.Before:
After:
Why are the changes needed?
Improve error messages readability.
Does this PR introduce any user-facing change?
Improve error messages readability.
How was this patch tested?
Unit tests
Was this patch authored or co-authored using generative AI tooling?
No